Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In
`@packages/cozy-search/src/components/CreateAssistantSteps/useAssistantDialog.js`:
- Around line 64-70: handleProviderSelection currently preserves
apiKey/encryptedApiKey, allowing stale credentials to bypass validation in edit
flow; update setFormData inside handleProviderSelection to also clear credential
fields (set apiKey to an empty string and encryptedApiKey to a falsy value)
whenever the provider changes so EditAssistantDialog.jsx's
!!formData.encryptedApiKey cannot be satisfied by a previous provider's key.

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@packages/cozy-search/src/components/CreateAssistantSteps/ApiKeyStep.jsx`:
- Around line 37-46: The TextField for provider name is incorrectly wired to
onChange('model') which mutates formData.model; change it to update a dedicated
field (e.g. onChange('providerName') or onChange('name')) or make the field
readOnly depending on desired UX. Locate the TextField in ApiKeyStep.jsx
(props/locals: providerName, onChange) and: if providerName should be editable,
add/use a separate form key (providerName/name) in formData and replace
onChange('model') with onChange('providerName') (and update any form handling to
include that key); if it should be fixed, set the TextField to readOnly/disabled
and remove the onChange handler to prevent accidentally mutating formData.model.
Ensure form submission and validation use the new dedicated field instead of
formData.model.

---

Nitpick comments:
In `@packages/cozy-search/src/locales/en.json`:
- Around line 130-131: The placeholder text for the "placeholder" field under
the "label": "Model" entry is awkward and can confuse provider vs model; update
the placeholder string (the "placeholder" key in the same JSON entry) to a
clearer variant such as "Enter the model name" or "Enter the provider's model
name" to tighten copy and remove ambiguity.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/cozy-search/src/components/CreateAssistantSteps/ApiKeyStep.jsx`:
- Line 18: The inputs for provider name, model, and baseUrl are rendering from
selectedProvider but updates only write to formData, causing the UI and
submitted payload to diverge; update the ApiKeyStep component so these inputs
are driven from formData (not directly from selectedProvider) or ensure
selectedProvider is updated when the user edits the fields. Concretely, change
the value props for the name/model/baseUrl inputs (currently using
selectedProvider or destructured id,name,model,baseUrl) to read from formData
(e.g. formData.providerName/formData.model/formData.baseUrl) and keep onChange
handlers updating formData, or alternatively wire the existing model-selection
update path used by AssistantDialogContent (the model-selection handlers around
AssistantDialogContent.jsx:35-42) to also set selectedProvider when the form
inputs change; make the same change for all three input groups referenced (lines
around 37-46, 55-64, 73-81) so displayed values and the submitted payload remain
in sync.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/cozy-search/src/components/CreateAssistantSteps/ApiKeyStep.jsx`:
- Line 13: AssistantDialogContent is still passing the removed onModelSelect
prop into the ApiKeyStep component; remove the unused prop from the ApiKeyStep
invocation in AssistantDialogContent.jsx so the call matches ApiKeyStep's
signature ({ apiKey, selectedProvider, onChange }). Locate the JSX element that
renders <ApiKeyStep ... /> in AssistantDialogContent and delete the
onModelSelect={...} attribute (or any variable passed as onModelSelect) to stop
passing the dead prop and eliminate prop warnings.

In `@packages/cozy-search/src/components/CreateAssistantSteps/providers.json`:
- Around line 3-8: The provider entry for "openrag" is missing the baseUrl
property which causes useAssistantDialog.handleProviderSelection to copy an
undefined provider.baseUrl into formData and CreateAssistantDialog to submit
formData.baseUrl as undefined; either restore a baseUrl field in the "openrag"
object inside providers.json (e.g., add "baseUrl": "<Twake endpoint>") or update
useAssistantDialog.handleProviderSelection and CreateAssistantDialog to stop
copying/sending baseUrl and instead derive the endpoint solely from providerId
("openrag"); modify the code paths referenced by
useAssistantDialog.handleProviderSelection and CreateAssistantDialog to keep
behavior consistent with the chosen approach.

In `@packages/cozy-search/src/components/Views/CreateAssistantDialog.jsx`:
- Around line 64-65: When building the submit payload in
CreateAssistantDialog.jsx (inside the onSubmit handler) guard against a null
selectedProvider before accessing selectedProvider.id; update the payload
creation that currently uses selectedProvider.id to use a safe access pattern
(e.g., optional chaining selectedProvider?.id or fallback value) and/or validate
selectedProvider and early-return or show an error if it is null, so
formData.isCustomModel and providerId are always set without throwing.

---

Outside diff comments:
In `@packages/cozy-search/src/components/CreateAssistantSteps/ApiKeyStep.jsx`:
- Around line 37-46: The TextField for provider currently reads from
providerName (selectedProvider.name) but writes to formData.model via
onChange('model'), causing a controlled input mismatch; update bindings so read
and write target the same state: either make the field display-only by keeping
value={providerName} and remove or replace onChange with a no-op/display
handler, or make it editable by changing value to the corresponding formData
property (e.g., value={formData.model}) and keep onChange={onChange('model')};
apply the same fix to the baseUrl and model TextField instances so each
TextField's value prop and onChange refer to the same state identifiers
(selectedProvider.name vs formData.baseUrl/formData.model).

Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@packages/cozy-search/src/components/CreateAssistantSteps/useAssistantDialog.js`:
- Around line 43-47: When providerId changes we must clear provider-scoped
secrets so stale apiKey/encryptedApiKey aren't submitted: update
handleProviderSelection (and the form update path used in edit mode) to reset
formData.apiKey and formData.encryptedApiKey (and any other provider-scoped
fields) whenever providerId (or selectedProvider?.id) is changed; ensure the
same clearing logic runs before canSubmit is evaluated so switching to
STEPS.MODEL_SELECTION with selectedProvider.id === 'openrag' or switching
between external providers cannot reuse the previous provider's credentials.

---

Duplicate comments:
In `@packages/cozy-search/src/components/CreateAssistantSteps/ApiKeyStep.jsx`:
- Line 18: The inputs in ApiKeyStep (the destructured selectedProvider: id,
providerName, model, baseUrl) are bound to selectedProvider while onChange only
updates formData, causing read-only behavior in edit mode; update the input
value props to read from formData (e.g., formData.providerId,
formData.providerName, formData.model, formData.baseUrl) or alternatively call
the same onChange handler to keep selectedProvider in sync on every edit, and
ensure AssistantDialogContent/ EditAssistantDialog pass formData down into
ApiKeyStep so the component binds and submits the same state.